Skip to content

[fivetran] Revamp docs#5777

Open
koletzilla wants to merge 24 commits intomainfrom
clickhouse/improve-fivetran-docs
Open

[fivetran] Revamp docs#5777
koletzilla wants to merge 24 commits intomainfrom
clickhouse/improve-fivetran-docs

Conversation

@koletzilla
Copy link
Copy Markdown
Contributor

@koletzilla koletzilla commented Mar 18, 2026

Revamp Fivetran docs:

  • Index cover more details about the current version and related files
  • Reference covers all the docs we have in Fivetran side: configurations, table engine details...
    • I have not moved the full setup-guide, only the configurations details. The full guide should be kept complete in Fivetran side as it's really nice to have it when editing the connector.
  • Troubleshooting contains usual errors with possible solutions, good practices and some examples to help debugging.

@vercel
Copy link
Copy Markdown

vercel bot commented Mar 18, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
clickhouse-docs Ready Ready Preview, Comment Mar 31, 2026 10:19am
clickhouse-docs-jp Building Building Preview, Comment Mar 31, 2026 10:19am
3 Skipped Deployments
Project Deployment Actions Updated (UTC)
clickhouse-docs-ko Ignored Ignored Preview Mar 31, 2026 10:19am
clickhouse-docs-ru Ignored Ignored Preview Mar 31, 2026 10:19am
clickhouse-docs-zh Ignored Ignored Preview Mar 31, 2026 10:19am

Request Review

Copy link
Copy Markdown
Collaborator

@dhtclk dhtclk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a few minor nits on voice and grammar, as well as the use of the note admonition.

@koletzilla
Copy link
Copy Markdown
Contributor Author

Thanks for all these suggested changes @dhtclk 🙇

Copy link
Copy Markdown
Contributor

@BentsiLeviav BentsiLeviav left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left a few comments/questions.
In addition, can we go over the code and track errors we raise, and document them with an explanation in the troubleshooting guide? (if they are not here already)

@koletzilla
Copy link
Copy Markdown
Contributor Author

@BentsiLeviav I have checked the errors sent by the server and I feel most of them should not be documented, but I have included in the Troubleshooting section a few ones.

Included:

  • Grants tests failing.
  • Error while waiting for all mutations to be completed.
  • Column mismatch/Type incompatibility/Column not found.

Not included:

  • Related to configuration: All shown in the UI during test
    • Host should not contain protocol or port: already included in the web
    • Host should not contain path
    • Port must be a number in range [1, 65535]
    • Failed to parse advanced config
    • Configuration value out of allowed range
  • Related to connection errors: Needs basic checks
    • Error while opening a connection to ClickHouse
    • ClickHouse connection error
    • Connection test failed
  • Related to cluster & replication errors: Situation controlled
    • Error while waiting for all nodes to be available
  • Related to data processing errors: internal fivetran error that a user doesn't have control of and may be fixed after a retry.
    • Can't parse value
    • No target type for column
    • Batch operation errors
    • Retry exhaustion
    • Failed to write batch / Failed to write history batch
  • Related to table operation errors: Shouldn't happen, but as these are grants related, it's explained in the grant section
    • Failed to create table
    • Failed to alter table
    • Failed to truncate
  • Related to file processing errors: Internal errors to manage with Fivetran
    • Failed to open / decrypt / decompress CSV file
    • Empty CSV file without header

For future reference in case of needed: this is the full .md generated by Claude for all the errors mentioned: error-reference.md

Copy link
Copy Markdown
Collaborator

@dhtclk dhtclk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just did another small pass and pointed out a few corrections, once these are done I'll approve so you're not double blocked.

@koletzilla koletzilla force-pushed the clickhouse/improve-fivetran-docs branch from a952d15 to 49b7eae Compare March 31, 2026 10:04
koletzilla and others added 3 commits March 31, 2026 12:04
Co-authored-by: Dominic Tran <dominic.tran@clickhouse.com>
…oting.md

Co-authored-by: Dominic Tran <dominic.tran@clickhouse.com>
…oting.md

Co-authored-by: Dominic Tran <dominic.tran@clickhouse.com>
@koletzilla
Copy link
Copy Markdown
Contributor Author

Thanks again for checking it, @dhtclk! I appreciate your willingness to unlock the PR, but I'd like to wait for full approval from @BentsiLeviav just to confirm that the content is aligned with expectations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants